Secure transmission

ABSTRACT

A method for providing evidential data is disclosed. The method includes establishing one or more first secret tokens with a server; obtaining one or more data items from one or more sensors; modifying the one or more data items with at least one of the one or more first secret tokens to provide one or more modified data items; generating a respective first hash value for each of the one or more modified data items; generating a second hash value for a data set including each of the one or more data items; and transmitting the one or more data items, the one or more first hash values, and the second hash value to the server.

BACKGROUND

Mobile computing devices, such as mobile telephones, smartphones, tabletcomputers, etc., often comprise, or have access to, an array of sensorssuch as image sensors and sound sensors. While commonly used to recordevents for personal consumption, such recordings are generallyunsuitable for use as evidence in proceedings in which the authenticity,accuracy and/or provenance of those recordings may require verification.

The rapid proliferation of mobile devices is such, however, that mobiledevices are often present in circumstances in which such evidential datamay be usefully obtained. It would therefore be beneficial if suchmobile devices were able to obtain and provide evidential qualityrecordings of transactions or events. Such evidential quality recordingsmay have uses, for example, in legal proceedings, insurance claims, etc.

It is an object of the present invention to obviate or mitigate at leastone of the problems of the prior art whether identified herein orelsewhere.

SUMMARY

According to a first aspect described herein, there is provided a methodfor providing evidential data, comprising at a mobile device:establishing one or more first secret tokens with a server; obtainingone or more data items from one or more sensors; modifying the one ormore data items with at least one of the one or more first secret tokensto provide one or more modified data items; generating a respectivefirst hash value for each of the one or more modified data items;generating a second hash value for a data set comprising each of the oneor more data items; and transmitting the one or more data items, the oneor more first hash values and the second hash value to the server.

The data set may comprise the first hash values.

The method may further comprise obtaining one or more transactionidentifiers, each transaction identifier being suitable for identifyinga property of the mobile device; and transmitting an indication of thetransaction identifiers to the server.

The data set may comprise one or more of the transaction identifiers.

The one or more transaction identifiers may comprise one or more staticidentifiers, wherein each static identifier is suitable for identifyinga static property of the mobile device.

Transmitting an indication of the static identifiers to the server maycomprise generating a respective third hash value for each of the one ormore static identifiers, wherein the indication comprises the third hashvalues.

The data set may comprise the third hash values.

Calculating each respective third hash value may comprise modifying eachof the plurality of static identifiers with at least one of the one ormore first secret tokens and calculating each of the third hash valuesbased upon the modified static identifiers.

The transaction identifiers may comprise one or more variableidentifiers and each variable identifier may be suitable for identifyinga variable property of the mobile device. Transmitting an indication ofthe variable identifiers to the server may comprise transmitting thevariable identifier to the server.

The data set may comprise the variable identifiers.

The method may further comprise an initialization procedure. Theinitialization procedure may comprise transmitting a plurality ofinitialization identifiers to the server.

The initialization identifiers may comprise one or more staticidentifiers and/or one or more variable identifiers.

Transmitting a plurality of initialization identifiers may compriseobtaining the plurality of initialization identifiers, encrypting theobtained initialization identifiers and transmitting the encryptedinitialization identifiers to the server.

The transaction identifiers may be based upon the initializationidentifiers to allow comparison at the server between values of theinitialization identifiers and the transaction identifiers.

The one or more sensors may comprise at least one sensor from the groupcomprising a camera of the mobile device and a microphone of the mobiledevice.

The one or more data items may comprise one or more still images.

The one or more data items may comprise one or more videos.

The one or more data items may comprise one or more sound recordings.

The one or more static identifiers may comprise at least one identifierfrom the group comprising an identification number of a battery of themobile device, an IMEI number of the mobile device, and a telephonenumber of the mobile device.

The one or more variable identifiers may comprise at least oneidentifier from the group comprising a geographical location of themobile device, a date and time reported by the mobile device, a durationof time since the mobile device was turned on, an indication of otherdevices detected by the mobile device, and a file structure of themobile device.

The method may further comprise establishing one or more second secrettokens with the server after transmission of the one or more data itemsand the first and second hash values.

According to a second aspect, there is provided a method for receivingevidential data comprising, at a server: establishing one or more firstsecret tokens with a mobile device; receiving one or more data items,one or more first hash values, and a second hash value from the mobiledevice; wherein each of the one or more first hash values are hashvalues generated based upon a respective one of the one or more dataitems modified with at least one of the one or more first secret tokens;wherein the second hash value is a hash value generated based upon adata set comprising each of the one or more data items.

The method may further comprise modifying each of the received one ormore data items with at least one of the one or more first secrettokens; generating a respective first comparison hash value for each ofthe modified received one or more data items; comparing each respectivefirst comparison hash value to a corresponding one of the first hashvalues; and providing an indication for each respective first comparisonhash value that does not match a corresponding one of the first hashvalues.

Providing an indication may comprise outputting an indication to adisplay device, or saving an indication together with the data.

The method may further comprise receiving a plurality of initializationidentifiers from the mobile device; receiving one or more transactionidentifiers, each of the one or more transaction identifiers beingsuitable for identifying a property of the mobile device; and comparingat least one of the initialization identifiers with at least one of thetransaction identifiers.

The method may further comprise transmitting a request for thetransaction identifiers based upon the received initializationidentifiers.

The initialization identifiers may comprise a first static identifiersuitable for identifying a static property of the mobile device. The oneor more transaction identifiers may comprise an indication of acorresponding static identifier. Comparing at least one of theinitialization identifiers may comprise comparing the first staticidentifier with the corresponding static identifier.

The indication of the static identifier may comprise a third hash valuebased upon the corresponding static identifier. Comparing the firststatic identifier with the corresponding static identifier may comprisegenerating a fourth hash value based on the first static identifier andcomparing the fourth hash value with the third hash value.

The third hash value may have been generated by the mobile deviceperforming the steps of modifying the corresponding static identifierwith at least one of the one or more first secret tokens and calculatingeach the third hash values based upon the modified corresponding staticidentifier. Generating the fourth hash value may comprise modifying thefirst static identifier with at least one of the one or more firstsecret tokens and calculating the fourth hash value based upon themodified first static identifier.

The initialization identifiers may comprise a first variable identifiersuitable for indicating variable properties of the mobile device. Thereceived transaction identifiers may comprise a corresponding variableidentifier. Comparing the first variable identifier with thecorresponding variable identifier may comprise determining whether adifference between the first variable identifier and the second variableidentifier are within predetermined bounds.

The initialization identifiers may comprise at least one of a number ofa battery of the mobile device, an IMEI number of the mobile device, anda telephone number of the mobile device.

The one or more variable identifiers may comprise at least oneidentifier from the group comprising a geographical location of themobile device, a date and time reported by the mobile device, a durationof time since the mobile device was turned on, an indication of otherdevices detected by the mobile device, and a file structure of themobile device.

The method may further comprise establishing one or more second secrettokens with the mobile device after receipt of the one or more dataitems and the first and second hash values.

According to a third aspect, there is provided an apparatus forproviding evidential data, comprising a memory storing computer readableinstructions configured to cause a computer to carry out a method asdefined above, and a processor configured to execute the computerreadable instructions.

It is to be understood that features described with reference to oneaspect above may be combined with other aspects.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments of the invention are now described, by way of example only,with reference to the accompanying drawings, in which:

FIG. 1 schematically illustrates an example network of components whichmay be used to implement an embodiment;

FIG. 2A schematically illustrates an example configuration componentswhich may be used to implement the server of FIG. 1;

FIG. 2B schematically illustrates an example configuration of componentswhich may be used to implement a mobile device of FIG. 1;

FIG. 3 is a flowchart showing initiation processing carried out by theserver and the mobile device of FIG. 1;

FIG. 4 is a flow diagram showing data generated and exchanged betweenthe server and the mobile device while performing the processing of FIG.3;

FIG. 5 is a flowchart showing processing carried out by the mobiledevice of FIG. 1 to transmit evidential data;

FIG. 6 is a flow diagram showing how the data is bundled whileperforming the processing of FIG. 5; and

FIG. 7 is a flowchart showing processing carried out by the server toreceive evidential data from the mobile device.

DETAILED DESCRIPTION

FIG. 1 illustrates a network of computer devices that can be used toimplement embodiments of the present invention. A mobile device 1connects to a server 2 via a network 3. The network 3 may be anysuitable public or private network and may be, for example, theInternet. The mobile device 1 may take any form suitable for connectionto the network 2. For example, the mobile device 1 may be a mobiletelephone, a smartphone, a tablet, etc.

The connections between the server 2, the mobile device 1, and thenetwork 3 may take any appropriate form and may be wired or wirelessconnections. It will be appreciated that while a single mobile device 1is illustrated in FIG. 1, this is merely exemplary and any number ofmobile devices may connect with the server 2.

The mobile device 1 is configured to provide data to the server 2 viathe network 3. In particular, the mobile device 1 is configured toprovide data relating to incidents that occur in the proximity of themobile device 1, such as accidents, crimes, etc., for the purpose ofevidence. For example, the mobile device 1 may be equipped withrecording means such as one or more cameras for recording images orvideo, microphones for recording sounds, and receivers for recordingreceived radio signals. It will be appreciated that the mobile device 1may be used to obtain any form of evidential data as required.

The mobile device 1 may communicate with the server 2 from within alocal computer application operating on the mobile device 1 (or “app”)or via a remote application provided by the server 2 and accessed fromthe mobile device 1 through, for example, a web browser. Futurereferences to a computer application with which the mobile device 1 maycommunicate with the server 2 may therefore be either a local computerapplication or a remote application.

Upon obtaining evidential data, the mobile device 1 transmits theevidential data to the server 2 via the network 3. In particular, themobile device 1 transmits the evidential data along with further data toallow the server 2 and/or third parties (such as police or judicialauthorities) to determine that the evidential data originates from themobile device 1 and has not been modified, or otherwise tampered, withsubsequent to its creation and/or transmission to the server 2.

The server 2 is connected to a public data store 4 and a private datastore 5. The private data store 5 may be isolated from the network 3 toprevent access to files stored thereon by, for example, the mobiledevice 1, and any other device. A firewall 6 may be connected betweenthe private data store 5 and the server 2.

The mobile device 1 may operate in the vicinity of one or more locationindication devices. As used herein, the term location indication devicemeans any device which may be used to provide indications of the currentgeographical location of the mobile device 1 or indications ofgeographical locations through which the mobile device 1 has passed. Forexample, the mobile device 1 may pass in and out of range of one or morewireless access points or base stations 7, 8 (such as WiFi access pointsand/or WiMAX base stations, for example), one or more global positioningsatellites (GPS) 9, and one or more cellular network antennas 10.

FIG. 2A shows an exemplary schematic illustration of components whichcan be used to provide the mobile device 1 in accordance with someembodiments of the present invention. It can be seen that the mobiledevice 1 comprises a CPU 1 a which is configured to read and executeinstructions stored in a random access memory (RAM) 1 b which, in thisexample, takes the form of volatile memory 1 b. It will be appreciatedthat non-volatile RAM may equally be used in such an embodiment. The RAM1 b stores instructions for execution by the CPU 1 a and data used bythose instructions. For example, the instructions loaded into the RAM 1b may provide one or more computer programs that are operable to obtainevidential data and to transmit that evidential data to the server 2.

The mobile device 1 further comprises non-volatile storage 1 c, whichmay take any suitable form, such as, for example, a hard disk drive(HDD) or solid state drive (SSD). Computer readable instructions forfacilitating the capture, storage and transmission of evidential data tothe server 2 may be stored in the non-volatile storage 1 c.

The mobile device 1 further comprises an I/O interface 1 d to which areconnected peripheral devices used in connection with the mobile device1. More particularly, a display 1 e is configured so as to displayoutput from the mobile device 1. The display 1 e may be a touchscreendisplay, allowing a user to provide input to the mobile device 1 e.Other input devices are also connected to the I/O interface 1 d. Suchinput devices include a camera 1 f and a microphone 1 g, therebyallowing a user of the mobile device 1 to obtain images (including videoand still) and sound. It will be appreciated that other input devicesmay equally be provided. For example, dedicated biometric scanningmeans, such as fingerprint scanners, may be provided.

A network interface 1 h allows the mobile device 1 to be connected toappropriate computer networks, such as the network 3, so as to receiveand transmit data from and to other computing devices such as the server2. The network interface 1 h may also allow connection with, ordetection of signals from, location indication devices such as thelocation indication devices 7 to 10.

The CPU 1 a, volatile memory 1 b, RAM 1 c, I/O interface 1 d, andnetwork interface 1 h, are connected together by a bus 1 i.

It will be appreciated that the arrangement of components illustrated inFIG. 2A is merely exemplary, and that the mobile device 1 may compriseadditional or fewer components than those illustrated in FIG. 2A.

FIG. 2B shows a schematic illustration of components which can be usedto provide the server 2 in accordance with some embodiments of thepresent invention. It can be seen that, at a schematic level, the server2 may be implemented similarly to the mobile device 1. In particular,the server 2 may comprise a CPU 2 a which is configured to read andexecute instructions stored in a random access memory (RAM) 2 b. The RAM2 b stores instructions for execution by the CPU 2 a and data used bythose instructions. For example, the instructions loaded into the RAM 2b may provide one or more computer programs that are operable tofacilitate receipt of evidential data from the mobile device 1 and forconfirming that the received evidential data is suitable for use asevidence.

The server 2 further comprises non-volatile storage 2 c, which may takeany suitable form, such as, for example, a hard disk drive (HDD) orsolid state drive (SSD). The non-volatile storage 2 may comprise thedata stores 4, 5. Alternatively, the data stores 4, 5 may be connectedto the server 2 via a storage network (not shown).

The server 2 further comprises an I/O interface 2 d to which areconnected peripheral devices used in connection with the server 2. Moreparticularly, a display 2 e is configured so as to display output fromthe server 2. The display 2 e may be a touchscreen display, allowing auser to provide input to the server 2. Other input devices may alsoconnected to the I/O interface 2 d, such as a keyboard 2 f. It will beappreciated that other input devices may equally be provided.

A network interface 2 h allows the server 2 to be connected toappropriate computer networks, such as the network 3, so as to receiveand transmit data from and to other computing devices such as the mobiledevice 1.

The CPU 2 a, volatile memory 2 b, RAM 2 c, I/O interface 2 d, andnetwork interface 2 h, are connected together by a bus 2 i.

It will be appreciated that the arrangement of components illustrated inFIG. 2B is merely exemplary, and that the server 2 may compriseadditional or fewer components than those illustrated in FIG. 2B.Indeed, the server 2 may comprise a plurality of computers, similar to,or arranged differently from, the mobile device 1. For example, theserver 2 may comprise a plurality of computers respectively adapted toprovide, inter alia, a web server, an application server, a gatewayserver, and a database server, etc., to provide suitable applications tothe mobile device 1 over the network 3. That is, it is to be understoodthat, like the mobile device 1, the server 2 may be implemented usingany appropriate configuration as will be readily appreciated by thoseskilled in the art.

FIG. 3 is a flowchart illustrating an initialization process that iscarried out by the mobile device 1 and the server 2 before transactionsfor transmission of evidential data between the mobile device 1 to theserver 2. FIG. 4 schematically illustrates data that is generated andexchanged by the mobile device 1 and the server 2 during the processingof FIG. 3. It is assumed that in advance of the processing of FIG. 3, auser of the mobile device 1 has registered as a customer or user of aservice which receives evidential data. For example, the user of themobile device 1 may obtain an insurance product, such as vehicleinsurance, from an entity that operates the server 2 or on whose behalfthe server 2 is operated. In this example, the user 1 may useembodiments described herein to provide evidential data relating toaccidents, damage, etc. of a vehicle that is insured.

Prior to the processing of FIG. 3, the entity with whom the user isregistered may provide suitable login details for use of theapplication. Alternatively, the user may establish login details througha registration process conducted through the application, as will bereadily appreciated by the skilled person.

At step S1, the user of the mobile device 1 enters their login detailsinto a suitable interface provided by the application. At step S2, theserver 2 receives the user's login details and validates that the logindetails belong to a registered account. Following validation of thelogin details, from step S1, processing at the mobile device 1 passes tostep S3, while processing at the server 2 passes to step S4. At steps S3and S4 the mobile device 1 and the server 2 exchange public keys for usewith asymmetric cryptography. With reference to FIG. 4, the mobiledevice 1 transmits its public key 15 to the server 2, while the server 2transmits its public key 16 to the mobile device 1. In FIG. 4, theserver 2 is shown as receiving the public key 15 and the mobile deviceis shown as receiving the public key 16. It will be appreciated thatthis is merely schematic, and that the server 2 will maintain a copy ofthe public key 15 while the mobile device 1 will maintain a copy of thepublic key 16. The mobile device 1 further stores a private key 17(corresponding to its public key 15), while the server 2 stores aprivate key 18 (corresponding to its public key 16).

The keys 15, 16, 17, 18 may be generated prior to the processing of FIG.3 or may be generated as part of the processing of steps S3 and S4. Thepublic and private keys may be generated using any appropriate means aswill be readily apparent to the skilled person. As an example only, thepublic and private keys may be generated using the RSA algorithm.

Upon receipt of the public key 15 from the mobile device 1, processingat the server 2 passes to step S5 at which the server 2 generates aunique, randomly generated token 21. The token 21 is encrypted using thepublic key 15 received from the mobile device 1 to generate an encryptedtoken 22 which can only be decrypted using the private key 17 of themobile device 1. The token 21 (or data to be sent in combination withthe token 21) may additionally be signed (not shown in FIG. 4) by theserver 2 using the private key 18. For example, the token 21, or a hashof the token 21, may additionally be encrypted using the private key 18such that the token 21 can only be decrypted by the mobile device 1using the public key 16 received from the server 2. In this way, themobile device 1 can have greater certainty that the token 21 wasreceived from the server 2, and not a third party.

The encrypted token 22 is transmitted to the mobile device 1 andreceived by the mobile device 1 at step S7. The mobile device 1 decryptsthe encrypted token 22 using its private key 17 to obtain the token 21.

After the processing of steps S3 to S7, the mobile device 1 and theserver 2 each possess information, in the form of the token 21, knownonly to each other. It will be appreciated, however, that the processingof steps S3 to S7 are merely exemplary, and that in practice anysuitable means may be used for the mobile device 1 and the server 2 tosecurely exchange a suitable token. In other embodiments, for example, aplurality of secret tokens may be exchanged.

Processing passes from step S7 to step S8 at which the mobile device 1generates or obtains a plurality of initialization identification dataitems 25. Suitable identification data items include, for example, anInternational Mobile Station Equipment Identity (IMEI) number of themobile device 1 (or similar identifiers, such as ESN, MEID, etc.), anInternational Mobile Subscriber Identity (IMSI) number, Service SetIdentifier (SSID) history data (i.e., which SSIDs the mobile device 1has come into contact with), GPS data, an indication of a current localmobile cell, current date and time data, a recorded uptime of the mobiledevice 1, a last reboot time of the mobile device 1, a bit-rate betweenthe mobile device 1 and the server 2, a file directory structure of themobile device 1, etc. That is, it will be appreciated that theidentification data may comprise any suitable identification data whichcan be used by the server 2 to ascertain the authenticity of a deviceclaiming to be the mobile device 1 in future transactions.

The identification data may comprise both “static” identifiers and“variable” identifiers. Static identifiers may be identifiers which arenot expected to change over time or which are expected to change onlyinfrequently. For example, battery identification numbers, IMEI numbers,file structure data, etc. may be expected to vary infrequently. Variableidentifiers may be those identifiers which are expected to change overtime. For example, time and data identifiers, location identifiers, SSIDhistory data, etc. may be expected to vary between an initialization anda first transaction, and between respective transactions.

As is described below in more detail with reference to FIGS. 5 and 6,identifiers may be transmitted to the server 2 from the mobile device 1during each transaction (i.e., transactions to transmit evidentialdata). Because static identifiers are not expected to vary frequently,it may not be necessary to re-transmit (after initial transmissionduring the processing of FIG. 3) each static identifier. Rather, asdiscussed below, in some embodiments, only a hash value based on eachstatic identifier is transmitted.

The particular set of identification data items 25 obtained or generatedby the mobile device 1 may be selected randomly by the mobile device 1or by a user of the mobile device 1. Alternatively, the set ofidentification data items may be selected by the server 2 and sent as arequest to the mobile device 1. Alternatively, the set of identificationdata items may be agreed between the server 2 and the mobile device 1 ina handshake operation in which it is determined which data items can beprovided. For example, it will be appreciated that different devices(e.g., tablets and mobile telephones) may have different features whichlimit or facilitate the generation of one or more identification dataitems.

Having generated the identification data items 25, processing passesfrom step S8 to step S9 at which the identification data items 25 areencrypted to provide encrypted identification data items 26. In theexample embodiment shown in FIG. 4, the identification data items 25 areeach encrypted using the public key 16 of the server 2. It is to beappreciated, however, that the identification data items may beencrypted using any appropriate encryption scheme, or transmitted in anyappropriately secure manner. For example, the pre-shared token may beused as a symmetric encryption key, and the identification data itemsmay be encrypted using the pre-shared token. In other embodiments, theidentification data items 25 may not be encrypted before transmission tothe server 2.

The encrypted identification data items 26 are transmitted from themobile device 1 to the server 2. At step S10, the server 2 receives theencrypted identification data items 26 and, together with the privatekey 18, the server 2 decrypts the encrypted identification data items 26to obtain the data items 25.

With reference to FIGS. 5 and 6, there is now described processingperformed at the mobile device 1 for obtaining and transmittingevidential data to the server 2.

At step S15, the mobile device 1 obtains data 35 which is to be used forthe purpose of evidence. The data 35 may comprise a plurality of dataitems. For example, the data 35 may comprise one or more still imagesobtained using the camera 1 f of the mobile device 1, one or more videoscaptured using the camera 1 f, one or more sound records obtained withthe microphone 1 g, etc. Where the data 35 comprises one or more videorecordings, one or more of the video recordings may be separated intorespective frames.

Processing passes to step S16 at which a first data item from the data35 is selected. At step S17, the data item is combined with the token 21in order to generate a modified data item 36. The token 21 may becombined with the data item in any appropriate way, such as, forexample, prepending, appending, or distributing the token throughout thedata item according to a predetermined scheme known to both the mobiledevice 1 and the server 2. Processing passes from step S17 to step S18at which a hash value 37 is generated based upon the modified data item36. The hash value 37 maybe generated using any appropriate hashingalgorithm. As examples only, the widely used SHA1 or SHA2 hashingalgorithm, or the newer SHA3 algorithm, may be used.

Processing passes from step S18 to step S19 at which it is determinedwhether there are any further data items in the data 35. If it isdetermined that there are further data items, processing passes fromstep S19 to step S20 at which the next data item is selected. Processingpasses from step S20 to step S17. Processing therefore loops betweensteps S17 to S20 until each of the data items in the data 35 has beenprocessed so as to generate a plurality of respective modified dataitems 36 and a corresponding plurality of hash values 37.

When it is determined at step S19 that all data items in the data 35have been processed, processing passes to step S21, at which a singlehash value 38 is generated from a bundle comprising each data item inthe data 35. The data bundle may further comprise the hash values 37.The hash value 38 may be additionally or alternatively be generated fromthe data 35 combined in some, known way, with the token 21.

At step S22, the data 35, together with the hash values 37 and the hashvalue 38 is transmitted to the server 2. By transmitting each of thehash values 37, together with the hash value 38, the server 2 is able toperform an initial check (based on the hash value 38) that the data 35has not been modified. In particular, upon receipt of the data 35, theserver 2 is able to calculate a hash value that should have the samevalue as the hash value 38. If it is discovered that the data has beenmodified or corrupted (because the hash value calculated by the server 2does not match the hash value 38), because each of the hash values 37are also transmitted, it is possible for the server 2 to subsequentlyidentify exactly which of the data items in the data 35 has beenmodified, corrupted, or not transmitted by the mobile device 1.

Additionally, one or more identifiers 25′ may be transmitted along withthe evidential data at step S22. The identifiers 25′ may be referred toas transaction identifiers (as they are transmitted during atransaction) to distinguish them from the identifiers 25 which may bereferred to as initialization identifiers (as they are transmittedduring an initialization procedure).

The identifiers 25′ may comprise one or more of the same identifiers 25that are transmitted to the server 2 at step S10 of FIG. 3. For example,the server 2 may request, during a transaction, one or more specificidentifiers (such as the IMEI number of the mobile device 1), or mayrequest that identifiers corresponding to each of the identifiers 25 areincluded in the identifiers 25′. As described above, that while theidentifiers 25′ may include one or more of the same type of identifierincluded in the identifiers 25 (e.g., “date” type identifiers), it is tobe expected that the value of one or more of the identifiers may differbetween the identifiers 25 and the identifiers 25′. As described above,the identifiers which are expected to differ may be referred to asvariable identifiers.

Like the data items in the data 35, each of the identifiers 25′ mayadditionally be combined with the token 21 and hash values calculatedtherefrom in order to create a bundle of identifier hash values 39,which may be transmitted to the server 2. In some embodiments, one ormore of the hash values 39 are transmitted in place of the correspondingidentifier 25′. For example, where the identifier 25′ is a staticidentifier (such as an IMEI number, which may be expected to be the sameas it was when the corresponding identifier 25 was sent), a hash 39 ofthe static identifier may be transmitted to the server 2, in place ofre-sending the identifier. Where the static identifier is first modifiedusing the token 21, further checks may be performed by the server 2 toimprove confidence that the device transmitting the identifiers 25′ isthe mobile device 1.

The processing of FIG. 5 is such that when the data 35 is used asevidence, which may be after a period of storage at the server 2, theserver 2 can determine that the data 35 has not been tampered with orotherwise corrupted (i.e., that the data 35 is suitable for evidentialuses). In particular, as now described with reference to FIG. 7, onlythe server 2 is able to re-create the hash values 37, 38 based on thereceived data. That is, as only the server 2 knows the value of thetoken 21 (and the scheme used to combine the token 21 with the dataitems of the data 35), only the server is able to re-create the hashvalues. As such, successful re-creation of the hash values 37, 38 at theserver 2 is evidence that the data items are authentic and unmodified.Further, the identifiers 25′ and/or the identifier hash values 39 may beused to further confirm the identity of the mobile device 1.

In addition to, or as an alternative to, being transmitted to the server2, the hash values 37, 38, 39 may be transmitted to an independent thirdparty for secure storage until such a time as verification of the data35 is required. Where both the server 2 and a third party receive thehash values 37, 38, 39, verification of the data 35 may be performed byboth the server 2 and an independent third party. In an embodiment, someor all of the hash values 37, 38, 39 are sent only to the third party.In some embodiments, the server transmits token 21 to a third partywhich may be the same or a different third party to that which receivesthe hash values 37, 38, 39. It can be seen therefore, that independentverification of the data 35 may be provided by use of third partiesunrelated to either the user of the mobile device 1 or the entityassociated with the server 2.

FIG. 7 illustrates processing that may be carried out at the server 2upon receipt of evidential data from the mobile device 1 through theprocessing of FIG. 6. It will be appreciated the processing of FIG. 7,or similar processing may be carried out any stage after receipt of thedata from the mobile device 1. For example, the processing of FIG. 7 (orsimilar) may be deferred until the data is to be used in an evidentialfashion. For example, in the example above of vehicle insurance,processing to determine the veracity, authenticity, and trustworthinessof data received from the mobile device 1 may be deferred until aparticular claim is processed by an agent of the insurer, for example.

Referring to FIG. 7, at step S30, data sent by the mobile device 1 isreceived at the server 2. As described above, the data transmitted bythe mobile device 1 comprises the data that is to be used as evidence,together with a plurality of hash values 37 (a respective hash value foreach data item) and a single hash value 38 representing the data as abundle (which may or may not be combined with the token 21). Processingpasses from step S30 to step S31 at which the server 2 calculates atleast one hash value based upon the received data and the token 21stored at the server 2.

In particular, the server 2 may first calculate only the hash value 38.Respective hash values for each of the received data items may becalculated only in the event that the hash value 38 cannot be recreatedby the server 2 in order to determine which data items are suspect. Inother embodiments, the server 2 may calculate all of the hash values atthe outset.

After calculating the hash values, processing passes to step S32 atwhich the hash values calculated by the server 2 are compared with thehash values received from the mobile device 1. If it is determined atstep S32 that the hash values calculated by the server 2 do not matchthe hash values received from the mobile device 1, this indicates thatthe received data may have, for example, been modified, been corruptedduring transmission, or originated from a device other than the mobiledevice 1 (such that the other device did not know the value of thepre-shared token 21). Where the hash values do not match, this mayindicate that the data received at the server 2 is not suitable for useas evidence. Processing passes from step S32 to step S33.

At step S33, an indication is provided (for example, an indication maybe output to the display 2 e of the server 2, output to the display 1 emobile device 1, and/or saved together with the received data at theserver 2) that the calculated hash values do not match the received hashvalues. It will be appreciated that additional processing may beperformed upon determination at step S32 that the hash values do notmatch. For example, the received data may be rejected, and a message maybe sent from the server 2 to the mobile device 1 requesting that thedata be re-transmitted. Other processing that may be performed will bereadily apparent to the skilled person.

If, on the other hand, it is determined at step S32 that the hash valuescalculated by the server 2 do match the hash values received from themobile device 1, processing passes from step S32 to step S34 at which itis determined whether the one or more of the identifiers 25′ match theidentifiers 25 that were sent from the mobile device 1 to the server 2during the processing of FIG. 3 and/or whether the identifier hashvalues 39 match corresponding hash values calculated by the server 2based upon the identifiers 25 received during the processing of FIG. 3.It is to be understood that not all of the identifiers are necessarilychecked at step S34.

If it is determined at step S34 that the examined one or moreidentifiers 25′ do not match the corresponding identifiers 25 and/orthat the identifier hash values 39 do not match corresponding hashvalues calculated by the server 2 based upon the identifiers 25,processing passes from step S34 to step S35, at which indication isprovided (for example, an indication may be output on the server 2,output on the mobile device 1, or saved together with the received data)that the identifiers 25 do not match the identifiers 25′ and/or that thecalculated hash values do not match the received hash values 39. It willbe appreciated that additional processing may be performed at step S35.For example, the data may be rejected, and a message may be sent fromthe server 2 to the mobile device 1 requesting that the data bere-transmitted. Other processing that may be performed will be readilyapparent to the skilled person.

If, on the other hand, it is determined at step S34 that the receivedidentifiers 25′ do match the stored identifiers 25, and/or that thereceived hash values 39 do match the calculated hash values, processingpasses to step S36, at which the received data is stored for later use.Storage of the data may be, for example, on both the storage device 4and the storage device 5. Data stored on the storage device 4 may beaccessible (for example, for viewing, annotating, modification, etc.) bythe mobile device 1, while data stored at the storage device 5 may beinaccessible to the mobile device 1. In this way, data stored at thestorage device 5 may be used to confirm that data stored at the mobiledevice 4 has not been modified in such a way that it can no longer beused for evidential purposes.

After each receipt of data, a new token may be exchanged between theserver 2 and the mobile device 1 at step S35. As described above withreference to the processing of FIG. 3, a new token may be generated andexchanged in any appropriate way. For example, a new token may beselected randomly by one of the server 2 or the mobile device 1 andtransmitted to the other device using public key cryptography.Alternatively, the server 2 may be issue a new token to the mobiledevice 1, which the mobile device 1 salts with information known only tothe mobile device 1 and the server 2 (such as one of the identifiers 25,25′, a transaction number, etc.)

It will be appreciated, that even in the event that the data 35 isidentified as originating from the mobile device 1, and has not beenmodified or corrupted before receipt at the server 2, it may be furtherdesired to determine that the data 35 is trustworthy (i.e., that theuser of the mobile device 1 has not fabricated the data 35). As will bedescribed in more detail below, the identifiers 25′ may additionally beused to provide indications as to whether the data 35 is trustworthy.

After receiving data from the mobile device 1 during a transaction, theserver 2 may perform background processing to compare the identifiers 25with the identifiers 25′ to determine if the identifiers 25′ are validor plausible in light of the identifiers 25. For example, where theidentifiers 25 and 25′ each include one or more time-based identifiers(such as a current time or date), it may be determined whether thetime-based identifiers in the identifiers 25 precede the time-basedidentifiers in the identifiers 25′. As a further example, where theidentifiers 25, 25′ each include a location based identifier (such as aGPS location, a current cell location, etc.) it may be determinedwhether it is feasible that the mobile device 1 could have reached thelocation indicated in the identifiers 25′ given the location indicatedin the identifiers 25. Determining whether a location is feasible maycomprise comparing a distance between locations identified in each ofthe identifiers 25, 25′ with respect to a time indication. As a furtherexample, where the identifiers 25, 25′ include hardware identifiers ofthe mobile device 1 (for example, battery serial number, IMEI number,phone uptime, last reboot, start time, etc.), comparisons may be made toidentify inconsistencies.

It will be appreciated that a plurality of consistency checks may beperformed based upon the identifiers 25, 25′. It will further beappreciated that in many cases, the data received at the server 2 may beaccepted for storage even in the event of inconsistencies in theidentifiers 25, 25′, where inconsistencies are merely noted along withthe received data so that identified inconsistencies can be taken intoaccount when assessing whether the received data is suitable for use asevidence. In other embodiments, however, determined inconsistencies maybe used to automatically reject received data and/or trigger otherprocessing such as requests for additional information.

It is described above that the initialization process comprises theexchange of identifiers which are utilized for comparison in furthertransactions. In other embodiments, initialization does not comprise thetransfer of such identifiers. In some embodiments, identifiers may betransferred during each transaction and compared across differenttransactions.

In some embodiments, identifiers are transferred outside of transactionsor initialization procedures, such that the server 2 maintains aregularly updated copy of relevant identifiers. For example, anapplication operating on the mobile device 1 may be arranged to transferone or more identifiers to the server 2 in background processingoperations. Alternatively, the application may prompt a user of themobile device 1 to authorize transmission of identifiers outside oftransactions initiated by the user. Such prompts or backgroundprocessing operations may be at regular or random intervals.

It will be appreciated that aspects can be implemented in any convenientway, including by way of suitable hardware and/or software. For example,devices arranged to implement embodiments may be created usingappropriate hardware components. Alternatively, a programmable devicemay be programmed to implement embodiments.

The invention therefore also provides suitable computer programs forimplementing aspects. Such computer programs can be carried on suitablecarrier media including non-transitory carrier media (e.g., hard disks,CD ROMs, and so on).

It will further be appreciated that while example embodiments aredescribed above, modifications may be made to those examples withoutdeparting from the scope of the appended claims.

What is claimed is:
 1. A method for providing evidential data,comprising at a mobile device: establishing one or more first secrettokens with a server; obtaining one or more data items from one or moresensors; combining the one or more data items with at least one of theone or more first secret tokens to provide one or more modified dataitems; generating a respective first hash value for each of the one ormore modified data items; generating a second hash value for a data setincluding each of the one or more data items; transmitting a firstmessage comprising the one or more data items, the one or more firsthash values, and the second hash value to the server, wherein the firstmessage is usable by the server to authenticate the one or more dataitems; and establishing one or more second secret tokens with the serverafter transmission of the first message, the one or more second secrettokens for combining with one or more second data items obtained fromthe one or more sensors for generating a second message; obtaining oneor more transaction identifiers, the one or more transaction identifiersincluding one or more static identifiers; and transmitting an indicationof the static identifiers to the server, including generating arespective third hash value for each of the one or more staticidentifiers, wherein the indication includes the third hash values,wherein the one or more first secret tokens are pre-shared with theserver before transmitting the first message comprising the one or moredata items.
 2. The method of claim 1, wherein each transactionidentifier is suitable for identifying a property of the mobile device.3. The method of claim 2, wherein each static identifier is suitable foridentifying a static property of the mobile device.
 4. The method ofclaim 1, wherein calculating each respective third hash value includesmodifying each of the plurality of static identifiers with at least oneof the one or more first secret tokens and calculating each of the thirdhash values based upon the modified static identifiers.
 5. The method ofclaim 1, wherein: the transaction identifiers include one or morevariable identifiers and wherein each variable identifier is suitablefor identifying a variable property of the mobile device; andtransmitting an indication of the variable identifiers to the serverincludes transmitting the variable identifier to the server.
 6. Themethod of claim 1, further comprising: an initialization procedure, theinitialization procedure including transmitting a plurality ofinitialization identifiers to the server.
 7. The method of claim 6,wherein the initialization identifiers include one or more staticidentifiers and one or more variable identifiers.
 8. The method of claim6, further comprising: obtaining one or more transaction identifiers,each transaction identifier suitable for identifying a property of themobile device; and transmitting an indication of the transactionidentifiers to the server; wherein the transaction identifiers are basedupon the initialization identifiers to allow comparison at the serverbetween values of the initialization identifiers and the transactionidentifiers.
 9. The method of claim 1, wherein the one or more sensorsinclude at least one sensor from a group consisting of: a camera of themobile device and a microphone of the mobile device.
 10. The method ofclaim 1, wherein the one or more data items include at least one of: oneor more still images, one or more videos, or one or more soundrecordings.
 11. The method of claim 3, wherein the one or more staticidentifiers include at least one identifier from a group consisting of:an identification number of a battery of the mobile device, an IMEInumber of the mobile device, and a telephone number of the mobiledevice.
 12. The method of claim 5, wherein the one or more variableidentifiers include at least one identifier from a group consisting of:a geographical location of the mobile device, a date and time reportedby the mobile device, a duration of time since the mobile device wasturned on, an indication of other devices detected by the mobile device,and a file structure of the mobile device.
 13. A method for receivingevidential data comprising, at a server: establishing one or more firstsecret tokens with a mobile device; receiving one or more first dataitems, one or more first hash values, and a second hash value from themobile device in a first message usable by the server to authenticatethe one or more data items, the one or more first data items obtainedfrom one or more sensors; wherein each of the one or more first hashvalues are hash values generated based upon a respective one of the oneor more first data items combined with at least one of the one or morefirst secret tokens; wherein the second hash value is a hash valuegenerated based upon a data set including each of the one or more dataitems; establishing one or more second secret tokens with the mobiledevice after transmission of the first message, the one or more secondsecret tokens for combining by the mobile device with one or more seconddata items obtained from the one or more sensors for generating a secondmessage; receiving a plurality of initialization identifiers including afirst static identifier from the mobile device; receiving one or moretransaction identifiers including an indication of a correspondingstatic identifier which includes a third hash value based upon thecorresponding static identifier; and comparing the first staticidentifier with the corresponding static identifier, includinggenerating a fourth hash value based on the first static identifier andcomparing the fourth hash value with the third hash value, wherein theone or more first secret tokens are pre-shared with the mobile devicebefore receiving the first message comprising the one or more dataitems.
 14. The method of claim 13, further comprising: modifying each ofthe received one or more data items with at least one of the one or morefirst secret tokens; generating a respective first comparison hash valuefor each of the modified received one or more data items; comparing eachrespective first comparison hash value to a corresponding one of thefirst hash values; and providing an indication for each respective firstcomparison hash value that does not match a corresponding one of thefirst hash values.
 15. The method of claim 13 wherein each of the one ormore transaction identifiers is suitable for identifying a property ofthe mobile device.
 16. The method of claim 15, wherein the first staticidentifier is suitable for identifying a static property of the mobiledevice.
 17. The method of claim 13, wherein: the third hash value wasgenerated by the mobile device by modifying the corresponding staticidentifier with at least one of the one or more first secret tokens andcalculating each the third hash values based upon the modifiedcorresponding static identifier; and generating the fourth hash valueincludes modifying the first static identifier with at least one of theone or more first secret tokens and calculating the fourth hash valuebased upon the modified first static identifier.
 18. The method of claim13, wherein: the initialization identifiers include a first variableidentifier suitable for indicating variable properties of the mobiledevice; the received transaction identifiers include a correspondingvariable identifier; and comparing the first variable identifier withthe corresponding variable identifier includes determining whether adifference between the first variable identifier and the second variableidentifier is within predetermined bounds.
 19. A non-transitorycomputer-readable storage medium storing a set of instructions forexecution by a general purpose computer to provide evidential data at amobile device, the set of instructions comprising: a first establishingcode segment for establishing one or more first secret tokens with aserver; an obtaining code segment for obtaining one or more data itemsfrom one or more sensors; a modifying code segment for combining the oneor more data items with at least one of the one or more first secrettokens to provide one or more modified data items; a first generatingcode segment for generating a respective first hash value for each ofthe one or more modified data items; a second generating code segmentfor generating a second hash value for a data set including each of theone or more data items; a transmitting code segment for transmitting afirst message comprising the one or more data items, the one or morefirst hash values and the second hash value to the server, wherein thefirst message is usable by the server to authenticate the one or moredata items; a second establishing code segment establishing one or moresecond secret tokens with the server after transmission of the firstmessage, the one or more second secret tokens for combining with one ormore second data items obtained from the one or more sensors forgenerating a second message, a second obtaining code segment forobtaining one or more transaction identifiers, the one or moretransaction identifiers including one or more static identifiers; and asecond transmitting code segment for transmitting an indication of thestatic identifiers to the server, including generating a respectivethird hash value for each of the one or more static identifiers, whereinthe indication includes the third hash values, wherein the one or morefirst secret tokens are pre-shared with the server before transmittingthe first message comprising the one or more data.